Replace the flat 7-field Add Member detail with the full spec layout from
OP#871, reusing the per-line sub-models introduced by OP#876.

- Detail: add middle_name; demographics block (is_approximate_birthdate,
  age compute, birth_place, occupation_id, civil_status_id, income);
  area_id + address + email; latitude/longitude; one-to-many phone /
  bank / id_doc lines; membership_type_id (role); related mirror
  type_requires_head; computed roles_available and existing_membership_ids
  (read-only context table). member_name is now a stored compute of
  "FAMILY, GIVEN MIDDLE".
- Shared sub-models: make detail_id nullable on
  spp.cr.detail.create_group.{phone,bank,id_doc}, add a parallel
  add_member_detail_id FK, and an exactly-one-parent constraint so the
  same row shape can attach to either detail.
- Strategy: rewrite into _validate / _create_individual /
  _attach_phones|banks|id_docs / _demote_existing_head_if_needed /
  _create_membership. When the new member is added with the 'head' role,
  any existing head on the group is demoted automatically. Names are
  required; if the CR type sets requires_head, role assignment is too.
- View: full rewrite matching spec sections (Name, Demographics, Contact,
  Phone Numbers, Location, Financial Information, Identity Document,
  Members) with the review-stage banner "The following individual is to
  be added:" and a warning banner when requires_head is set.
- MIS demo generator: write membership_type_id instead of the removed
  relationship_id; drop the now-computed member_name from the payload.
- Tests: rewrite test_add_member_strategy.py against the new schema
  (basic create, name compute including middle name, age compute,
  validation paths, head demotion, sub-record attach); fix the four
  add_member call sites in test_e2e_workflows.py.

Stacks on top of feat/876-create-group-cr-redesign.

- Expose Allow Empty Groups / Requires Head of Household on the Change
  Request Type configuration form
- Collect the group address as a single field matching the registry
  (was split into Address Line 1/2, City, State, Postal Code, Country)
- Enforce one Head of Household at the member-row level so the rule also
  holds when rows are added through the member wizard
- Capture the full registry profile (names, demographics, contact) for a
  new individual in the Add New Individual modal
- Show "The following group is to be added" above the review table

…mber-cr-redesign

- Collect the member address as a single field matching the registry
  (was split into Address Line 1/2, City, State, Postal Code, Country)
- Make the existing-members table truly read-only — rows can no longer
  be opened and edited from the change request form
- Show "The following individual is to be added" above the review table
- Map approximate-birthdate to the registry individual on apply

Requires Head of Household is now configurable on the Change Request
Type form (merged from #876).

The Add New Individual modal now collects multiple phone numbers in an
editable list (matching the group's phone list) instead of a single
field. On apply, the numbers are folded (primary first) into the new
individual's single header phone field. The create-group phone row
model gained a member_new parent so the rows attach to the new member.

…mber-cr-redesign

# Conflicts:
#	spp_change_request_v2/details/create_group.py

…r (#876)

Editing a new in-group individual that already had phone numbers raised
"Exactly one parent must be set on a phone-number row". The wizard
rebuilt the list with a clear (5) command, which only nulls the phone
row's inverse FK instead of deleting it, momentarily orphaning the rows.
Use delete (2) commands so the old rows are removed cleanly.

…mber-cr-redesign

…i-parenting (#876)

The exactly-one-parent constraint also rejected zero-parent rows, which
Odoo can produce transiently while rewriting a one2many — surfacing a
confusing "Exactly one parent must be set" error to users editing a new
member's phone list. Only reject a row genuinely linked to more than one
record.

…mber-cr-redesign

# Conflicts:
#	spp_change_request_v2/details/create_group.py

…#876)

A new in-group individual's phone numbers are all folded into the
partner's single phone field, so there is no header-vs-other distinction
— the Primary toggle was meaningless. Remove it from the modal and join
the numbers in entry order.

…mber-cr-redesign

…hone rows (#876)

Root cause of the phone-row 'parent' errors: the Add New Individual
wizard is opened with a default_detail_id context (for the member row),
and the phone sub-model also has a detail_id field, so that default was
applied to the new phone rows — giving them two parents (detail_id +
member_new_id). Force detail_id=False when building the phone rows.
Adds a regression test that opens the wizard with the leaking context.

…hone rows (#876)

Root cause of the phone-row 'parent' errors: the Add New Individual
wizard is opened with a default_detail_id context (for the member row),
and the phone sub-model also has a detail_id field, so that default was
applied to the new phone rows — giving them two parents (detail_id +
member_new_id). Force detail_id=False when building the phone rows.
Adds a regression test that opens the wizard with the leaking context.

…ply (#876)

A new individual's captured phone numbers were only folded into the
partner's single header phone field, not created as spp.phone.number
records — so they didn't appear in the registry's Phone Numbers list.
Attach the phone records on apply, the same way the group's phones are
attached.

…mber-cr-redesign

…ember (#871)

When the target group already has a head, the Add Member form now shows
an info banner naming the current head and a 'Replace current Head of
Household' toggle. Replacement is no longer silent/automatic: giving the
new member the Head role while a head exists is blocked unless the toggle
is enabled; when enabled, applying demotes the current head and makes the
new member the head.

… is Head (#871)

The banner and Replace toggle now appear only when the picked Role is
Head AND the group already has a head. The toggle is purely a
confirmation gate: the picked Role determines the member's role, so a
stale toggle with a non-head role no longer forces head or demotes the
current head.

…ice (#871)

Drop the 'Replace current Head of Household' boolean. When the new member
is given the Head role and the group already has a head, the form now
shows a warning that applying will make this member the head and remove
the role from the current head; the replacement then happens
automatically on apply (the CR still passes through approval first).

…ew (#876)

The Create Group CR review page (review_comparison_html) showed only
counts for the one2many fields and omitted several group fields. Surface
the actual data via a generic render contract on preview():

- _tables: one2many fields render as their own tables - Phone Numbers,
  Bank Accounts, ID Documents, and Existing Members (Name / Role).
- _sections: new members render as a labelled detail block each, showing
  the full captured individual (role, DOB, gender, civil status,
  occupation, birth place, income, area, address, email) plus that
  member's own phone numbers.
- Add the previously-missing scalar fields: email, area, location.
- Drop the phone/bank/id_doc/member count keys.

_generate_review_comparison_html() renders _tables and _sections after
the action summary; _render_data_tables() / _render_data_sections() are
generic so other CR strategies can surface the same way.

…ber (#871)

The explicit head-of-household replacement feature (commits 908cedc,
1612822, a8c9b05) is deferred to #1006 ("make it configurable to
prevent groups without head of household"), which is on hold. Removing
it here per QA so #871 ships the Add Member review-page fix without it.

…mber-cr-redesign

… (#871)

The Add Member CR review page showed only counts for phones/bank/ID docs
and omitted the added individual's details. Surface the full data via the
generic _tables contract (shared with Create Group):

- All individual fields are shown even when empty (name, role, date of
  birth, gender, civil status, occupation, birth place, income, area,
  address, email, location).
- Phone Numbers / Bank Accounts / ID Documents render as their own tables.
- Drop the phone/bank/id_doc count keys.

The head-of-household replacement feature was reverted separately and
deferred to #1006.

Replace the single new-head dropdown with an editable members-with-roles
table: one role line is seeded per active group member, and the member
assigned the Head role becomes the new head (a constraint blocks two heads).
Make the current head non-clickable, drop the unused Effective Date field,
and remove the Voluntary Transfer reason.

Add reason-driven required documents: a per-reason document config on the
CR type (shown only for types whose detail exposes a reason) drives the
request's required documents via _get_effective_required_document_ids().

The review preview now renders the household, reason, remarks and a members
table (Name / Current Role / New Role).

Per the updated #871 spec, the Add Member CR first page now searches for an
existing individual registrant instead of building a new individual from
scratch.

- detail model: replace the create-new field set (names, demographics, phone/
  bank/ID lines) with an individual_id picker scoped by a computed domain to
  existing individuals not already in the group; keep the Role picker and the
  'no Head when the group already has one' restriction.
- strategy: apply() creates a membership for the selected individual; preview()
  reads the individual's fields and shows 'The following individual is to be
  added to the group'.
- view: first page is a member search + role.

Also update the MIS demo generator so its Add Member and Change Head of
Household change requests match the redesigned detail contracts (register the
individual then set individual_id; rebuild the change-of-head role lines).